Method for modeling vessel data model, method and device for collecting vessel data using vessel data model

ABSTRACT

The present invention relates to a method for collecting vessel data using a vessel data model (VDM), a device for collecting vessel data, and a vessel comprising same. Accordingly, it is preferable that the present invention comprises the steps of: acquiring vessel data generated from vessel equipment; and, on the basis of a VDM, converting the vessel data into integrated vessel data having an integrated format, and collecting same, wherein the VDM is generated by combining a vessel model, a system model and a data model, wherein the vessel model is a model defined by hierarchically classifying the vessel equipment, the system model is a model defined by structuring the vessel data, and the data model is a model for defining the attributes and types of the vessel data.

TECHNICAL FIELD

The present disclosure relates to a method and device for collectingvessel data using a vessel data model and a vessel comprising the same.

BACKGROUND ART

Vessels are categorized according to the purpose of use, the type ofcargo and the method by which the cargo is loaded, and vessels may beclassified into commercial vessels, specialized vessels, militaryvessels and fishing vessels according to the purpose of use, and may beclassified into container ships, bulk carriers, tankers, chemicaltankers, LPG carriers, LNG carriers and car carriers according to thetype of cargo.

Various types of vessels as described above each have a great deal ofsensors and devices mounted thereon to function for use that suits thepurpose.

Each sensor and device are collected and processed by integrationequipment and provided to a service necessary for safe navigation, andbecause one or more sensors and devices are made using differentprotocols for each manufacturer, it was not easy to collect data, andeven though data is collected, there is no method for managing thecollected data in an integrated manner, so there are many constraints ontransfer and utilization of the collected data not only on board butalso on shore.

Meanwhile, International Maritime Organization (IMO) compels thespecified “Maritime navigation and radiocommunication equipment andsystems” (e.g., Voyage Data Recorder (VDR), Integrated Navigation System(INS), etc.) to conform to International Electronical Committee (IEC)61162 based digital interfaces. Here, IEC 61162 is the communicationstandards for communication interfaces between “Maritime navigation andradiocommunication equipment and systems”, and IEC 61162 is aligned withthe National Marine Electronics Association (NMEA) standard.

In contrast, equipment (e.g., Alarm Monitoring System (AMS), BridgeManeuvering System (BMS), etc.) other than “Maritime navigation andradiocommunication equipment and systems” is not bound to conform to IEC61162. Additionally, there is a great limitation in expressing datausing the already published NMEA, and thus other industrial standards ora de facto standard is mainly selected and used.

By this reason, there is no common standard for interfacing betweenequipment other than “Maritime navigation and radiocommunicationequipment and systems”.

For example, the NMEA sentence structure receiving the position fromGlobal Positioning System (GPS) is as shown in FIG. 1. The NMEA sentenceis shared between system developers through a standard document, but anyindividual modification is not allowed.

When data to be used on the IEC 61162 standards is not data that ispredefined in NMEA sentence, is it is necessary to additionally performa task for defining the corresponding data in NMEA sentence under themutual agreement, and share through an interface agreement documentbetween them.

As described above, when data to be used on the IEC 61162 standards isnot predefined in NMEA sentence, there is inconvenience in having toadditionally define the data, write it in a document and share it.

Technical Problem

The present disclosure is designed to solve the above-described problem,and an object of the present disclosure is to provide a method forcollecting vessel data using a vessel data model, which converts vesseldata having different formats into integrated vessel data having anintegrated format based on a Vessel Data Model (VDM) and collects thesame.

Another object of the present disclosure is to provide a device forcollecting vessel data using a vessel data model, which converts vesseldata having different formats into integrated vessel data having anintegrated format based on a vessel data model and collects the same.

Still another object of the present disclosure is to provide a methodfor modeling vessel data model, which provides a vessel data model forstoring vessel data having different formats made by different protocolsinto an integrated data format.

SUMMARY OF THE INVENTION

To achieve the above-described object, a method for collecting vesseldata using a Vessel Data Model (VDM) according to an embodiment of thepresent disclosure includes acquiring vessel data generated from vesselequipment, and converting, on the basis of a VDM, the vessel data intointegrated vessel data having an integrated format, and collecting same,and preferably, the VDM is generated by combining a vessel model, asystem model and a data model, the vessel model is a model defined byhierarchically classifying the vessel equipment, the system model is amodel defined by structuring the vessel data, and the data model is amodel for defining the attributes and types of the vessel data.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, thevessel model is defined as vessel level, equipment group level,equipment level and component level, the vessel level is a level onwhich a vessel itself is defined, the equipment group level is a levelon which vessel equipment is grouped and defined as an equipment group,the equipment level is a level on which physical equipment, abstractequipment and logical equipment belonging to the equipment group aredefined as equipment, and the component level is a level on which theequipment is subdivided and defined as component.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, thesystem model is defined as system level, logical device level, logicalnode level and data object level, the system level is a level on which asystem for collecting vessel data is defined, the logical device levelis a level on which logical equipment belonging to the system is definedas logical device, the logical node level is a level on which an objectof function unit belonging to the logical device is defined as logicalnode, and the data object level is a level on which a type of vesseldata of the data model is defined as a data object.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, thelogical node includes Class that defines a type or category of thelogical node, and Inst that is a number necessary when indicatingmultiple objects.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, thelogical node further includes Prefix that defines a purpose or use ofthe logical node.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, a nameof the logical node is defined in an order of the Prefix, the Class andthe Inst, and the name is unique within a logical device to which thelogical node belongs.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, thedata model includes Data Class that defines a type of the vessel data,and Data Attribute that defines an attribute of the vessel data.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, thevessel model, the system model and the data model are combined by acombination model to generate the VDM, and the combination model setsconnection information for connecting the vessel model with the systemmodel.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, theVDM hierarchically defines paths leading to each vessel data, and eachvessel data is identified by VDM Path.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, theVDM Path includes at last one name of equipment group, equipment,component, logical device, logical node, data object and data attribute.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, theVDM Path has a sequential arrangement of at least one name of theequipment group, the equipment, the component, the logical device, thelogical node, the data object and the data attribute.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, theVDM Path is divided into VDM Path for data collection, and VDM Path fordata provision.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, theVDM Path for data collection includes at least one name of system,logical device, logical node, data object and data attribute.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, theVDM path for data provision includes a unique ID that identifies thevessel.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, therange of data provided hierarchically changes depending on hierarchylevel of the VDM Path for data provision.

In the method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure, preferably, theVDM is described in vessel data model configuration description languageto form a vessel data model configuration description file, and thevessel data model configuration description file includes definition ofvessel part, system part and data type part.

Meanwhile, a device for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure acquires vesseldata generated from vessel equipment, and on the basis of a VDM,converts the vessel data into integrated vessel data having anintegrated format and collects the same, and preferably, the VDM isgenerated by combining a vessel model, a system model and a data model,the vessel model is a model defined by hierarchically classifying thevessel equipment, the system model is a model defined by structuring thevessel data, and the data model is a model for defining the attributesand types of the vessel data.

Meanwhile, a method for modeling vessel data model according to anembodiment of the present disclosure preferably includes the vesselmodeling step of hierarchically classifying vessel equipment anddefining as a vessel model, the system modeling step of structuring datagenerated from the vessel equipment and defining as a system model, thedata modeling step of defining attribute of the data generated from thevessel equipment as a data model, and the combination modeling step ofcombining the vessel model, the system model and the data model to forma Vessel Data Model (VDM).

Advantageous Effects

According to the method and device for collecting vessel data using avessel data model in accordance with the present disclosure and thevessel comprising the same, it is possible to manage (collect, store,provide) all formats of vessel data made by different protocols into onesystem.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an exemplary diagram showing the conventional NMEA sentencestructure.

FIG. 2 is a diagram showing three elements of VDM according to anembodiment of the present disclosure.

FIG. 3 is a schematic diagram showing the structure system of VDMaccording to an embodiment of the present disclosure.

FIG. 4 is a UML diagram showing the vessel model hierarchy structure ofVDM according to an embodiment of the present disclosure.

FIG. 5 is a UML diagram showing the system model hierarchy structure ofVDM according to an embodiment of the present disclosure.

FIG. 6 is a data model UML diagram of VDM according to an embodiment ofthe present disclosure.

FIG. 7 is a combination model UML diagram of VDM according to anembodiment of the present disclosure.

FIG. 8 is a diagram showing a relationship between a system model and adata model of VDM according to an embodiment of the present disclosure.

FIG. 9 is a diagram showing a relationship between VCL and a vessel datamodel configuration description file according to an embodiment of thepresent disclosure.

FIGS. 10 to 12 are diagrams illustrating VDM Path according to anembodiment of the present disclosure.

FIG. 13 is a processing diagram illustrating a method for modelingvessel data model according to an embodiment of the present disclosure.

FIG. 14 is a processing diagram illustrating the vessel modeling step(S100) of FIG. 13.

FIG. 15 is a processing diagram illustrating the system modeling step(S200) of FIG. 13.

FIG. 16 is a processing diagram illustrating the data modeling step(S300) of FIG. 13.

FIG. 17 is a processing diagram illustrating the combination modelingstep (S400) of FIG. 13.

FIG. 18 is a processing diagram illustrating a method for collectingvessel data using a vessel data model according to an embodiment of thepresent disclosure.

FIG. 19 is a schematic diagram showing the configuration of a device forcollecting vessel data using a vessel data model according to anembodiment of the present disclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereinafter, a method and device for collecting vessel data using avessel data model according to a preferred embodiment of the presentdisclosure and a vessel comprising the same will be described in detailwith reference to the accompanying drawings.

In describing the embodiments of the specification, when a certaindetailed description of relevant known elements or functions isdetermined to render the subject matter of the present specificationvague, the detailed description may be omitted herein.

The terms “comprises” and “comprising” as used herein specify thepresence of stated functions, operations and elements, but do notpreclude the presence or addition of one or more other functions,operations and elements. Additionally, it should be understood that theterm “comprises” or “includes” when used in this specification specifiesthe presence of stated features, figures, steps, operation, elements,components or groups thereof, but does not preclude the presence oraddition of one or more other features, figures, steps, operation,elements, components or groups thereof. As used herein, the singularforms are intended to include the plural forms as well, unless thecontext clearly indicates otherwise.

The key terms as used herein are defined as follows.

Vessel data integration platform (VDIP) is for collecting, processing,analyzing, storing and transmitting various vessel data, and refers toany system including software, firmware and hardware devices that managevessel data in an integrated manner or their selective combinations, ormay be used in software sense.

Vessel data model (VDM) is a data model for defining all data associatedwith the vessel into one system, and objectifies all devices rangingfrom the vessel itself to an end sensor and defines a relationshipbetween objects and attributes of objects.

Vessel data model configuration description Language (VCL) is thelanguage used to write a vessel data model configuration descriptionfile for describing VDM.

Vessel data model configuration description file is a configuration filethat describes VDM in VCL.

Mapping configuration description file is a file that defines a rule forconverting equipment output data into VDM based integrated vessel data.

Mapping is a process of connecting equipment output data to VDM.

Equipment is mounted on the vessel for a special purpose, and collectsvarious vessel data generated in the vessel, and transmits the collectedvessel data to VDIP.

Raw data is data in various formats collected by equipment from sensorsor devices.

Hereinafter, the present disclosure is described with reference to theaccompanying drawings.

First, to realize the embodiments of the present disclosure, it isnecessary to manage vessel data into one system to collect and use allformats of data generated in the vessel.

That is, vessel data generated in the vessel includes various types ofdata such as sensor data generated from a sensor attached to equipmentin the vessel, configuration data used in equipment, condition data ofequipment, alarm data representing error information, metadata thatdescribes data, and design data.

Currently, vessel data is made by different protocols for eachmanufacturer.

Accordingly, a standard that can manage various formats of vessel datainto one system is established to improve the efficiency and economicefficiency of data processing.

Vessel data has a close relationship with the shipbuilding industry andthe characteristics of vessels, and the standard system of vessel datashould consider this feature. A summary of the shipbuilding industry andthe characteristics of vessels is as follows.

Shipbuilding industry is a typical custom-making industry in which allspecifications may be determined by the customer. In many cases,specifications are determined within a predetermined range, but the casein which specifications fall outside the predetermined range cannot beexcluded.

Vessels have some characteristics of residences, offices, factories andwarehouses where sailors reside and work, and besides, have essentialrequirements that are unique to vessels; floatability, loadability,mobility and stability. To implement this, a variety of many mechanical,electrical, hydraulic, pneumatic, electronic, communication or S/Wequipment is mounted in vessels.

Vessels are classified according to the purpose of use, the type ofcargo and the method by which the cargo is loaded. Vessels includecommercial vessels, specialized vessels, military vessels and fishingvessels according to the purpose of use, and include container ships,bulk carriers, tankers, chemical tankers, LPG carriers, LNG carriers andcar carriers according to the type of cargo.

The configuration, specification, arrangement and combination of allinternal equipment changes depending on the customer's needs and thetype of vessel. That is, each shipping line has its unique systemarchitecture. In addition, as individual equipment also has differentcharacteristics for each manufacturer and each model, all these factorsaffect data configuration.

Assumption that can be derived through the shipbuilding industry and thecharacteristics of vessels as described above is as follows.

As the external environment for defining vessel data always changes, itis necessary to consider the influences of a ship type difference, ashipping line difference and new equipment introduction in advance.

There is uncertainty that is uncontrollable by manufacturers cannotcontrol, and thus, the premises are modification and adaptation.

Hereinafter, a vessel data model (VDM) that is established to managevessel data based on a common model, considering the shipbuildingindustry and the characteristics of vessels as described above, will bedescribed.

As shown in FIG. 2, VDM largely has three conceptual categories, and thethree concepts are vessel data standardization principle (Principle),Language and Common Data Structure.

First, the vessel data standardization principle (Principle) that buildsa system for commonly representing and exchanging all formats of datagenerated in the vessel is as follows.

VDM conforms to the following.

Common and general knowledge and classification systems that can beaccepted as widely as possible in the shipbuilding or vessel domain arepursued, while avoiding dependency on particular systems and providers.

VDM is configured in reusable form to facilitate the continuous use andenable the adaptation to changes.

To represent vessel data, VDM defines a combination of three models,Vessel Model of modeling Vessel Part, System Model of modeling SystemPart, and Data Model of modeling Data Type Part as shown in FIG. 3.

Vessel Model

System Model

Data Model

The vessel model is a hierarchical classification system of equipmentthat constitutes the vessel, and is an entire set of equipment that canbe defined for each level, and the entire set can be extended.

As shown in Table 1, the vessel model may be defined as four levels.Each of the four levels is:

Level 1: Vessel

Level 2: Equipment Group

Level 3: Equipment

Level 4: Component.

TABLE 1 Level Name Description Remarks Level 1 Vessel Vessel. Top-levelelement Level 2 Equipment Group Conceptual group of equipment Level 3Equipment Real equipment or abstract/ logical equipment Level 4Component Subdivision of Equipment Optional

FIG. 4 is a Unified Modeling Language (UML) diagram showing the vesselmodel hierarchy structure of VDM, in which Vessel has one or moreEquipment Groups, each Equipment Group has 0 or more Equipment, and eachEquipment has 0 or more Component (see FIG. 3).

Here, the highest level, Level 1, is Vessel that signifies the vesselitself. Vessel includes an IMO number corresponding to a unique ID thatidentifies the vessel.

Instances of Level 2, Equipment Group level, make up one Vessel. Here,Equipment Group is subordinate to Vessel.

Level 2, Equipment Group, is a conceptual group of Level 3, Equipment,and uses the group name widely used for classification in theshipbuilding industry. For example, classification into Machinery, Hull,Electrical, and Navigational may be used.

Level 3, Equipment, is a level that mainly represents real equipment,and has the largest number of available items and instances in realequipment.

The Equipment level is not limited to only real equipment, and mayrepresent abstract or logical equipment. For example, not only realphysical equipment such as engines or boilers, but also abstract/logicalconcept such as stability indication and loading status may be applied.

Level 4, Component, is an optional level used when subdividing Equipmentinto smaller parts, and is used when classification and reuse is neededdue to independency of Component itself or when the scale of Equipmentitself is large. For example, in the case of the engine, many cylinders,auxiliary machines and piping systems form a huge integrated system, sowhen each is subdivided into components and defined, making it possibleto classify under necessary viewpoints and separately use.

For example, the vessel model may be defined as shown in Table 2.

TABLE 2 Vessel Model Equipment Group Equipment Component MachineryMachinery equipment Diesel engine Steam turbine Gas turbine, multipleshafts Hydraulic motor . . . Pressurized equipment Pressure vesselContainer Well . . . . . . . . . Electrical Switchgear Switchboard Motorcontrol center Motor starter . . . Electric rotating machines Electricmotor Generator . . . . . . Navigational Charts Electronic chart displayand information system (ECDIS) Positioning equipment Global positioningsystem (GPS) Differential global positioning system (DGPS) . . . Headinginformation Gyro compass equipment . . . Speed measuring Electromagneticlog equipment Doppler log . . . . . . . . . . . . . . . . . .

The entire vessel model set described above can be continuouslyextended.

Meanwhile, the system model is a structured logical model for datagenerated from the equipment that constitutes the vessel.

Mechanical, electrical, hydraulic, pneumatic, electronic, communicationor software (S/W) equipment exists together in the vessel, and datagenerated from the equipment is collected by devices (InformationTechnology (IT), electronic and S/W equipment) capable of collectingdata.

The system model is used to define an internal data model for data thatcan be collected in the individual data collection devices.

The system model increases the reusability of the data model and managesthe variability in the data collection device. For example, the datacollection device, equipment A, is a device that collects data relatedto the engine and the piping system, the device's own logical model forthe engine and the piping system may be established in the device.Additionally, when the data collection device, equipment B, is a devicethat mainly collects data related to navigation, a logical model mainlyabout navigation data will be established. In case that equipment Bneeds to collect some of the data of equipment A in the future, it ispossible to reuse the model in such a way that equipment B may importand use the logical model of equipment A.

As shown in Table 3, the system model may be defined as four levels.Each of the four levels is:

Level 1: System

Level 2: Logical Device

Level 3: Logical Node

Level 4: Data Object.

TABLE 3 Level Name Description Remarks Level 1 System System Level 2Logical Device Top-level logical equipment modeling Level 3 Logical NodeBasic unit of logical function Level 4 Data Object Instance of data type

FIG. 5 is a UML diagram showing the system model hierarchy structure ofthe vessel data model, in which System has one or more Logical Devices,each Logical Device has one or more Logical Nodes, and each Logical Nodehas one or more Data Objects.

Level 1, System level, represents a data collection device (equipment),and includes one or multiple logical devices.

Level 2, Logical Device level, is the highest-level concept of logicalequipment modeling, and includes one or multiple logical nodes.

Logical Device may include, for example, models of main engine,generator engine, boiler, tank and positioning device defined in System,and may be a model of concept of their combination.

Level 3, Logical Node level, includes objects that are created bymodeling the function units of the vessel domain, and is the mostfundamental level of VDM. Logical Node may include the following threeelements.

Prefix: prefix (optional) that defines Logical Node according to thepurpose or use of Logical Node

Class: indicates the type or category of Logical Node

Inst: number necessary when indicating multiple objects

The Logical Node name (LNName) of is defined as <prefix>+<class>+<inst>,and this combination should be unique within a logical device to whichthe corresponding logical node belongs. For example, three pumps used inCentral CFW system may be modeled using a predefined Pump Class, andeach may be referred to as CentralCFWPump1, CentralCFWPump2, andCentralCFWPump3 so that they can be distinguished from other pumps usingthe prefix CentralCFW. If there is no overlap, CentralCFW may beomitted, and each may be defined as Pump1, Pump2, and Pump3.

Class of Logical Node is the key element of standardization thatencourages to predefine and use the objects of the essential functionunits of the vessel domain.

Level 4, Data Object level, is the most basic unit of dataconfiguration, and objectifies and defines Data Class of Data Model.

Meanwhile, the data model provides the means for creating a desired dataobject by providing a method that can define not only basic data type,but also their combination, or a composite data type.

When the system model is a structured logical model for data generatedfrom equipment that constitutes the vessel, the data model is a modelthat represents the generated data itself, and the data type may bedefined by recursive structurization. The data model increases thereusability of the data type and manages the variability.

This data model may include the following elements.

Data Class

Data Attribute

Recursion of Data Attribute (optional)

Basic Data Type

FIG. 6 is a UML diagram of data model, and Data Object of system modelassigns an ID to objectify and define Data Class of the data model.

Data Class is a data type in which data attributes are grouped into ameaningful combination.

Data Attribute is the most basic unit of the data model and can berecursively defined, and finally, has one of basic data types (Float,Timestamp, String, . . . ) as a type.

As described above, VDM includes a vessel model, a system model and adata model, and these three models are combined to form a VDM.

The basic principle of a combination model that combines the threemodels described above is as follows.

Vessel model systematically classifies and hierarchically divides thevessel.

System model defines a logical node of logical equipment in a particularsystem.

Data model defines data class of data object of system model.

Instance of equipment or component level of vessel model may beconnected with logical node of system model as shown in FIG. 7.

Connection information for connecting vessel model with logical node ofsystem model may be set.

Connection information indicates system and logical device forconnection of an only logical node.

Data object of system model objectifies data class of data model asshown in FIG. 8.

Each instance (object) defined by VDM as noted above is assigned with anobject identifier for uniquely identifying each instance (object), anddata attribute is defined.

VDM refers to the object identifier as VDM Path. That is, the VDM Pathis used as a unique identifier for particular data in the vessel.

For example, the rule of the VDM Path is as follows.

<VDM Path>=<Equipment Group Name>/<Equipment Name>/<ComponentName>/<Logical Device Name>/<Logical Node Name>.<Data ObjectName>.[<Data Attribute Name>]+

Here, <Logical Node Name> is composed of <prefix>+<class>+<inst>, and +following [<Data Attribute Name>] represents one or more repetitions.

Vessel Model System Model Data Model Equipment Equipment ComponentLogical Logical Node Name Data Data Group Name Name Device Prefix ClassInstance Object Attribute Name Name Name Name

The VDM Path of this rule may or may not include the prefix of equipmentand component of the vessel model and logical device and logical node ofthe system model if necessary.

The data attribute defines attributes that data of a correspondinginstance should have.

As described above, vessel data summarized by VDM should be described inthe form that can be understood by both the system and the interestparties, and to this end, VCL is defined.

VCL is the language used to write a vessel data model configurationdescription file for describing VDM, and the present disclosure does notlimit VCL to a particular type and may use all languages satisfying thefollowing specification as VCL.

It is possible to describe all elements of vessel model, system model,data model.

It is possible to set the values of attributes that each element has,and extend the attributes.

It is possible to describe the combination model.

In an embodiment of the present disclosure, XML (eXtensible MarkupLanguage) Schema Definition (XSD) is used as VCL satisfying theabove-described specification. As shown in FIG. 9, a vessel data modelconfiguration description file (e.g., VDM Configuration XML) may bewritten based on VCL.

The vessel data model configuration description file is a configurationfile that describes VDM in VCL, and includes definition of Vessel Part,System Part and Data Type Part as shown in FIG. 9.

Accordingly, as shown in FIG. 10, it is possible to extract VDM from avessel data model configuration description file that describes VDM inVCL, and extract VDM Path and data attributes from the extracted VDM.

For example, VCL may be defined as shown in Table 4.

TABLE 4 File name Description VCL.xsd Main VCL syntax definitionVCL_Vessel.xsd Vessel model syntax definition VCL_System.xsd Systemmodel syntax definition VCL_DataTypeTemplate.xsd Data model syntaxdefinition VCL_BaseType.xsd Basic complex type definition VCL_Enum.xsdUsed XML schema enumeration VCL_BaseSimpleType.xsd Basic simple typedefinition

Meanwhile, Common Data Structure of VDM summarizes vessel data, andsummarizes a necessary common and reusable structure. The common datastructure is largely summarized into the following two classes.

Class of Logical Node

Data Class

Class of Logical Node described above may be defined, for example, asshown in Table 5, and Data Class may be defined, for example, as shownin Table 6.

TABLE 5 Class Data Object Data Attribute Type Pump Mode.run stValBoolean Mode.abnormal stVal Boolean Mode.fail stVal BooleanIntel1.Temperature val Float hh.stVal Boolean hi.stVal Boolean . . . . .. . . . . . . . . .

TABLE 6 Analog Data Class Data Attribute Name Description Type RemarksDesc Description String description Val Value Float/Integer data QQuality ENUMERATED T TimeStamp Level Level Structure data Alarm AlarmStructure alarm Unit Unit ENUMERATED config rangeCfg RangeConfigStructure config smpRate Sampling Rate Integer config

Meanwhile, the VDM Path is used as an identifier that is unique toparticular data in the vessel as previously described, and may be usedas a routing rule for indicating particular vessel data on VDM.

Accordingly, in transmitting and receiving vessel data based on VDM,VDIP may identify each vessel data according to the VDM Path.

As shown in FIG. 10, the VDM Path may be divided into “VDM Path forequipment data collection” and “VDM Path for service data provision”.

The “VDM Path for equipment data collection” reflects the levels ofSystem Part and Data Type part as shown in FIG. 11.

The structure system of the “VDM Path for equipment data collection” isas follows (see FIG. 11).

<System Name>/<Logical Device Name>/<Logical Node Name>.<Data ObjectName>.[<Data Attribute Name>]+

Here, <Logical Node Name> is composed of <prefix>+<class>+<inst>, and +represents one or more repetitions.

The “VDM Path for equipment data collection” of the structure systemdescribed above may or may not include the prefix of System, LogicalDevice and Logical Node of System Part level if necessary.

Additionally, the “VDM Path for equipment data collection” may reflectall the levels of Vessel Part, System Part and Data Type Part.

In this case, the structure system of the “VDM Path for equipment datacollection” is as follows.

<Equipment Group Name>/<Equipment Name>/<Component Name>/<Logical DeviceName>/<Logical Node Name>.<Data Object Name>.[<Data Attribute Name>]+

Here, <Logical Node Name> is composed of <prefix>+<class>+<inst>, and +represents one or more repetitions.

The “VDM Path for equipment data collection” of the structure systemdescribed above may or may not include the prefix of Equipment andComponent of Vessel Part level and Logical Device and Logical Node ofSystem Part level if necessary.

Meanwhile, the “VDM Path for service data provision” reflects the levelsof Vessel Part, System Part and Data Type Part.

The structure system of the “VDM Path for service data provision” is asfollows (see FIG. 12).

<Equipment Group Name>/<Equipment Name>/<Component Name>/<Logical DeviceName>/<Logical Node Name>.<Data Object Name>.[<Data Attribute Name>]+

Here, <Logical Node Name> is composed of <prefix>+<class>+<inst>, and +represents one or more repetitions.

The “VDM Path for service data provision” of the structure systemdescribed above may or may not include the prefix of Equipment andComponent of Vessel Part level and Logical Device and Logical Node ofSystem Part level if necessary.

As shown in FIG. 12, the range of data provided hierarchically changesdepending on the hierarchy level of VDM Path used for service dataprovision. For example, when an input of ‘Machinery/Machineryequipment/Diesel engine’ as VDM Path is received from a 3^(rd) partyservice, all information associated with diesel engine is provided tothe 3^(rd) party service, and when an input of ‘Machinery/Machineryequipment/Diesel engine/Pump1’ as VDM Path is received from a 3^(rd)party service, information associated with pump1 in the diesel engine isprovided to the 3^(rd) party service.

Additionally, it is possible to manage a set of necessary VDM Paths toprovide a particular customized service to a 3^(rd) party service.

When providing vessel data for an onshore service, a unique ID foridentifying the vessel, vessel IMO number (e.g., 1111111), is added infront of the VDM Path.

FIG. 13 is a processing diagram illustrating a method for modelingvessel data model according to an embodiment of the present disclosure.

The method for modeling vessel data model according to an embodiment ofthe present disclosure includes the vessel modeling step (S100) ofhierarchically classifying vessel equipment and defining as a vesselmodel, the system modeling step (S200) of structuring data generatedfrom the vessel equipment and defining as a system model, the datamodeling step (S300) of defining attributes of the data generated fromthe vessel equipment as a data model, and the combination modeling step(S400) of combining the vessel model, the system model and the datamodel to form a VDM.

As shown in FIG. 14, the vessel modeling step (S100) described above mayinclude the vessel definition step (S110) of defining the vessel, theequipment group definition step (S120) for grouping equipment of thevessel and defining as an equipment group, the equipment definition step(S130) of defining physical equipment, abstract equipment and logicalequipment belonging to the equipment group as equipment, and thecomponent definition step (S140) of subdividing the equipment intocomponents and defining as component.

As shown in FIG. 15, the system modeling step (S200) described above mayinclude the system definition step (S210) of defining a data collectiondevice for collecting vessel data as system, the logical devicedefinition step (S220) of defining the highest-level concept of logicalequipment belonging to the system as logical device, the logical nodedefinition step (S230) of defining object of function unit belonging tological device as logical node, and the data object definition step(S240) of objectifying data class of the data model and defining as dataobject.

As shown in FIG. 16, the data modeling step (S300) may include the dataclass definition step (S310) of combining data attributes and definingas data class, and the data attribute definition step (S320) of definingdata attribute of instance.

As shown in FIG. 17, the combination modeling step (S400) describedabove may include the step (S410) of connecting instance of equipment orcomponent level of the vessel model with logical node of the systemmodel, and the step (S420) of setting connection information forconnecting the instance of equipment or component level of the vesselmodel with the logical node of the system model.

FIG. 18 is a processing diagram illustrating a method for collectingvessel data using a vessel data model according to an embodiment of thepresent disclosure.

The method for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure includes the step(S500) of acquiring vessel data generated from vessel equipment, and thestep (S600) of converting vessel data into integrated vessel data havingan integrated format based on VDM and collecting the same.

FIG. 19 is a schematic diagram showing the configuration of a device forcollecting vessel data using a vessel data model according to anembodiment of the present disclosure.

The device for collecting vessel data using a vessel data modelaccording to an embodiment of the present disclosure acquires vesseldata (raw data) generated from vessel equipment, such as alarm data,sensor data and configuration data, and converts the vessel data intointegrated vessel data having an integrated format based on VDM andcollects the same.

As described above, the collected integrated vessel data converted intoan integrated format may be transmitted to an onshore management system,or may be provided to a 3^(rd) party service.

The method for collecting vessel data and the method for modeling vesseldata model as noted above may be implemented as an application or in theform of program commands that can be executed through various computercomponents, and recorded in computer-readable recording media. Thecomputer-readable recording media may include program commands, datafiles and data structures, alone or in combination.

The program commands in recorded in the computer-readable recordingmedia may be specially designed and configured for the presentdisclosure, and may be known and available to those having ordinaryskill in the field of computer software.

Examples of the computer-readable recording media include hardwaredevices specially designed to store and execute program commands, suchas magnetic media such as hard disk, floppy disk and magnetic tape,optical recording media such as Compact Disc Read Only Memory (CD-ROM)and Digital Versatile Disc (DVD), magneto-optical media such asfloptical disk, and ROM, Random Access Memory (RAM) and flash memory.

Examples of the program commands include machine codes generated by acompiler as well as high-level language codes that can be executed by acomputer using an interpreter. The hardware device may be configured toact as one or more software modules to perform processing according tothe present disclosure, or vice versa.

Additionally, the method and device for collecting vessel data using avessel data model may be implemented in the form of software andfirmware that manages vessel data in an integrated manner and beprovided in the vessel, and may be implemented as any system includingsoftware, firmware and hardware devices that manages vessel data in anintegrated manner or their selective combinations and be provided in thevessel.

Those having ordinary skill in the technical field pertaining to thepresent disclosure will appreciate that various modifications andchanges may be made without departing from the essential nature of thepresent disclosure. Additionally, the embodiments disclosed in thespecification and drawings are only a particular embodiment presented toeasily describe the disclosure and help the understanding of the presentdisclosure, but not intended to limit the scope of the presentdisclosure. Therefore, it should be interpreted that the scope of thepresent disclosure cover the embodiments disclosed herein as well as allmodified or changed forms derived based on the technical spirit of thepresent disclosure.

INDUSTRIAL APPLICABILITY

According to the method and device for collecting vessel data using avessel data model in accordance with the present disclosure and thevessel comprising the same, it is possible to manage (collect, store,provide) all formats of vessel data made by different protocols into anintegrated data format.

1. A method for collecting vessel data using a Vessel Data Model (VDM),comprising: acquiring vessel data generated from vessel equipment; andconverting, on the basis of a VDM, the vessel data into integratedvessel data having an integrated format, and collecting same, whereinthe VDM is generated by combining a vessel model, a system model and adata model, the vessel model is a model defined by hierarchicallyclassifying the vessel equipment, the system model is a model defined bystructuring the vessel data, and the data model is a model for definingthe attributes and types of the vessel data.
 2. The method forcollecting vessel data using a vessel data model according to claim 1,wherein the vessel model is defined as vessel level, equipment grouplevel, equipment level and component level, the vessel level is a levelon which a vessel itself is defined, the equipment group level is alevel on which vessel equipment is grouped and defined as an equipmentgroup, the equipment level is a level on which physical equipment,abstract equipment and logical equipment belonging to the equipmentgroup are defined as equipment, and the component level is a level onwhich the equipment is subdivided and defined as component.
 3. Themethod for collecting vessel data using a vessel data model according toclaim 1, wherein the system model is defined as system level, logicaldevice level, logical node level and data object level, the system levelis a level on which a system for collecting vessel data is defined, thelogical device level is a level on which logical equipment belonging tothe system is defined as logical device, the logical node level is alevel on which an object of function unit belonging to the logicaldevice is defined as logical node, and the data object level is a levelon which a type of vessel data of the data model is defined as a dataobject.
 4. The method for collecting vessel data using a vessel datamodel according to claim 3, wherein the logical node includes Class thatdefines a type or category of the logical node; and Inst that is anumber necessary when indicating multiple objects.
 5. The method forcollecting vessel data using a vessel data model according to claim 4,wherein the logical node further includes Prefix that defines a purposeor use of the logical node.
 6. The method for collecting vessel datausing a vessel data model according to claim 5, wherein a name of thelogical node is defined in an order of the Prefix, the Class and theInst, and the name is unique within a logical device to which thelogical node belongs.
 7. The method for collecting vessel data using avessel data model according to claim 1, wherein the data model includes:Data Class that defines a type of the vessel data; and Data Attributethat defines an attribute of the vessel data.
 8. The method forcollecting vessel data using a vessel data model according to claim 1,wherein the vessel model, the system model and the data model arecombined by a combination model to generate the VDM, and the combinationmodel sets connection information for connecting the vessel model withthe system model.
 9. The method for collecting vessel data using avessel data model according to claim 1, wherein the VDM hierarchicallydefines paths leading to each vessel data, and each vessel data isidentified by VDM Path.
 10. The method for collecting vessel data usinga vessel data model according to claim 9, wherein the VDM Path includesat last one name of equipment group, equipment, component, logicaldevice, logical node, data object and data attribute.
 11. The method forcollecting vessel data using a vessel data model according to claim 10,wherein the VDM Path has a sequential arrangement of at least one nameof the equipment group, the equipment, the component, the logicaldevice, the logical node, the data object and the data attribute. 12.The method for collecting vessel data using a vessel data modelaccording to claim 9, wherein the VDM Path is divided into VDM Path fordata collection, and VDM Path for data provision.
 13. The method forcollecting vessel data using a vessel data model according to claim 12,wherein the VDM Path for data collection includes at least one name ofsystem, logical device, logical node, data object and data attribute.14. The method for collecting vessel data using a vessel data modelaccording to claim 12, wherein the VDM path for data provision includesa unique ID that identifies the vessel.
 15. The method for collectingvessel data using a vessel data model according to claim 12, wherein therange of data provided hierarchically changes depending on hierarchylevel of the VDM Path for data provision.
 16. The method for collectingvessel data using a vessel data model according to claim 1, wherein theVDM is described in vessel data model configuration description languageto form a vessel data model configuration description file, and thevessel data model configuration description file includes definition ofvessel part, system part and data type part.
 17. (canceled)
 18. Acomputer-readable recording medium having recorded thereon a computerprogram for performing the method for collecting vessel data accordingto claim
 1. 19. A device for collecting vessel data using a vessel datamodel, which acquires vessel data generated from vessel equipment, andon the basis of a VDM, converts the vessel data into integrated vesseldata having an integrated format and collects the same, wherein the VDMis generated by combining a vessel model, a system model and a datamodel, the vessel model is a model defined by hierarchically classifyingthe vessel equipment, the system model is a model defined by structuringthe vessel data, and the data model is a model for defining theattributes and types of the vessel data.
 20. (canceled)